Issue & Reproduction Steps

This PR has been created to test the functionality of the new Templates within CI. We ran into an issue with the unitTest that may be happening based on the number of transactions needed to process the TemplateToProcessSync.

phpunit tests/Feature/Templates/Api/ProcessTemplateTest.php --filter=testTemplateToProcessSync

Solution

• Skip testTemplateToProcessSync for now.

How to Test

1. Please ensure that you have the Templates env variables within PM.

DEFAULT_TEMPLATE_REPO=process-templates
DEFAULT_TEMPLATE_BRANCH=develop
DEFAULT_TEMPLATE_CATEGORIES=all

2. Wipe the database and reinstall PM. (You should see 20 templates only)
3. Now change in the .env the default branch to DEFAULT_TEMPLATE_BRANCH=Templates-08-04-2023
4. Please verify that we have 41 templates and that we don't have any duplicates within the templates tab.

Related Tickets & Packages

• Ticket FOUR-9814
• Package process-templates

CI

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.